Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature/template #40

Open
wants to merge 41 commits into
base: main
Choose a base branch
from
Open

Feature/template #40

wants to merge 41 commits into from

Conversation

karpikpl
Copy link
Collaborator

@karpikpl karpikpl commented Sep 28, 2022

Template for starting with CoreEx

Things to complete:

  • Readme file for the template
  • Readme file for Azure DevOps pipelines
  • Test for running the template with latest coreEX
  • Github actions workflows - most likely to be completed in another PR

Piotr added 20 commits September 22, 2022 14:28
Signed-off-by: Piotr <[email protected]>
Signed-off-by: Piotr <[email protected]>
Signed-off-by: Piotr <[email protected]>
Signed-off-by: Piotr <[email protected]>
Signed-off-by: Piotr <[email protected]>
Signed-off-by: Piotr <[email protected]>
Signed-off-by: Piotr <[email protected]>
Signed-off-by: Piotr <[email protected]>
Signed-off-by: Piotr <[email protected]>
Copy link
Collaborator

@chullybun chullybun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we please move $\src\Templates to $\tools\CoreEx.Template where the project name is CoreEx.Template etc. as this will eventually be published as a NuGet package and should follow our CoreEx.* naming convention. This should be the same as NTangle for consistency. This way src is reserved for genuine runtime deployed packages only.

Piotr added 7 commits September 28, 2022 18:07
Signed-off-by: Piotr <[email protected]>
Signed-off-by: Piotr <[email protected]>
Signed-off-by: Piotr <[email protected]>
Signed-off-by: Piotr <[email protected]>
Signed-off-by: Piotr <[email protected]>

resources:
pipelines:
- pipeline: 'D365-Employee' # Name of the pipeline resource
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be renamed as D365 is not relevant?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

pipelines are work in progress - all those references will be removed

jobs:
- template: app-template.yml
parameters:
AzureSubscription: rg-priv-inte-dev-nte-na-01
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is name configurable? nte-na does not seem correct?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that will be deleted

},
"sources": [
{
// "modifiers": [
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should commented out content be removed?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was thinking that template eventually will be more dynamic, but not this week. We can remove or keep it on todo

@@ -0,0 +1,89 @@
namespace Company.AppName.Api.Controllers;

[Route("api/employees")]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Route contains api does this need to be amended like my.hr?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think function app adds /api but webapp doesn't

# deployToSlotOrASE: true
resourceGroupName: '$(ResourceGroupName)'
#slotName: '$(DeploymentSlot)'
package: '$(Pipeline.Workspace)/D365-Apps/D365-Apps_Package/Nte.Int.D365.Apps.FunctionApps.zip'
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another Nte reference

Piotr added 13 commits September 29, 2022 14:37
Signed-off-by: Piotr <[email protected]>
Signed-off-by: Piotr <[email protected]>
Signed-off-by: Piotr <[email protected]>
Signed-off-by: Piotr <[email protected]>
Signed-off-by: Piotr <[email protected]>
Signed-off-by: Piotr <[email protected]>
Signed-off-by: Piotr <[email protected]>
Signed-off-by: Piotr <[email protected]>
Signed-off-by: Piotr <[email protected]>
Signed-off-by: Piotr <[email protected]>
Signed-off-by: Piotr <[email protected]>
@karpikpl
Copy link
Collaborator Author

karpikpl commented Oct 4, 2022

@chullybun can you check if template project has been added correctly?

@chullybun
Copy link
Collaborator

@karpikpl - i built the solution from this branch, deployed all packages locally, installed the dotnet template, then executed to create Foo.Bar, opened the .sln in Visual Studio 2022, and ran the included unit tests all successfully - nice work👍

Pulumi, infra, etc. testing I will get to probably next week - we have Adi looking into that.

Was there anything else you wanted me to validate?

@karpikpl
Copy link
Collaborator Author

karpikpl commented Oct 7, 2022

I think that's it.
What wasn't working for me, was the running the template from nugget package due to OS permissions.

I've added a checklist on top on what is still pending.

@karpikpl
Copy link
Collaborator Author

If there's a risk of code going out of sync. maybe this can be merged and I can add other things as separate PRs?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants