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

Give me a way to bring in the "core" bicep files #2368

Closed
bradygaster opened this issue Jun 6, 2023 · 3 comments · Fixed by #2660
Closed

Give me a way to bring in the "core" bicep files #2368

bradygaster opened this issue Jun 6, 2023 · 3 comments · Fixed by #2660
Assignees

Comments

@bradygaster
Copy link

I'd love to have a way of doing something like azd init --core to lay down all the core infrastructure files when i set up a new AZD template. I typically start with my code, then i azd init, then i go pull from other places. it'd be nifty if there was either a switch on init or an additional to command to drop in all the core files.

@ghost ghost added the needs-triage For new issues label Jun 6, 2023
@savannahostrowski
Copy link
Contributor

We'd discussed adding core/ to the Bicep starter template. Might be worth doing that while we sort out the whole registry thing @ellismg.

@jongio
Copy link
Member

jongio commented Jun 6, 2023

As a workaround you can do azd init -t jongio/azd-starter-bicep-core, which is updated with latest from azure-dev/main

@ghost ghost removed the needs-triage For new issues label Jun 7, 2023
@rajeshkamal5050 rajeshkamal5050 added this to the October 2023 - 1.4.0 milestone Aug 24, 2023
@rajeshkamal5050
Copy link

Pulling this into next sprint since @aaronpowell was also requesting core/default ones to be available as part of starters.

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

Successfully merging a pull request may close this issue.

6 participants