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

Improvements to compose file scaffolding #2326

Closed
4 tasks
bwateratmsft opened this issue Sep 16, 2020 · 4 comments
Closed
4 tasks

Improvements to compose file scaffolding #2326

bwateratmsft opened this issue Sep 16, 2020 · 4 comments

Comments

@bwateratmsft
Copy link
Collaborator

bwateratmsft commented Sep 16, 2020

We discussed what we want for a user experience for Compose scaffolding.

  • Ability to add services to already-scaffolded compose files for all platforms (one service at a time)
    • Choose which compose file(s) to add the service to--allowing support for having many different compose files that launch different groups of services
  • Multiple-platform support, e.g. a compose file that references both .NET and Node projects
  • Samples for external services (e.g. database) that aren't being built (maybe best done in language server, Add intellisense for docker compose files #2539)
@bwateratmsft bwateratmsft added this to the 1.7.0 milestone Sep 22, 2020
@bwateratmsft bwateratmsft self-assigned this Sep 22, 2020
@bwateratmsft bwateratmsft modified the milestones: 1.7.0, Future Oct 1, 2020
@bwateratmsft
Copy link
Collaborator Author

Moving to future per our discussion. We'll await user feedback.

@bwateratmsft bwateratmsft removed their assignment Oct 9, 2020
@ucheNkadiCode
Copy link
Contributor

Adding specific note: Inserting snippet to add a "well known" service/image within a compose file. (Redis, postgres)

@bwateratmsft
Copy link
Collaborator Author

bwateratmsft commented Jan 13, 2021

Probably the best way to do that would be with the language server. I'll put a checkmark for it. #2539

@bwateratmsft
Copy link
Collaborator Author

Basically covered by #2539 so I'm going to close this one.

@bwateratmsft bwateratmsft removed this from the Future milestone Dec 2, 2021
@microsoft microsoft locked and limited conversation to collaborators Jan 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants