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

A list of breaking changes we're holding back for 6.0 #792

Closed
5 of 7 tasks
yob opened this issue Feb 3, 2021 · 9 comments
Closed
5 of 7 tasks

A list of breaking changes we're holding back for 6.0 #792

yob opened this issue Feb 3, 2021 · 9 comments

Comments

@yob
Copy link
Contributor

yob commented Feb 3, 2021

We have a few breaking changes we might make in 6.0, whenever that ends up being. I considered making a GitHub milestone for this list, but we don't have a culture of using them and I worried we might overlook it.

See also: Agent: A list of breaking changes we're holding back for 4.0

@nitrocode
Copy link
Contributor

Renaming SecurityGroupId to SecurityGroupIds would be good too

@woodhull
Copy link

woodhull commented Feb 9, 2021

Update docker to 20.x?

@chloeruka
Copy link
Contributor

Update docker to 20.x?

@woodhull Docker bumps are not usually considered breaking, are there significant implications of moving to v20?

@yob I'd also like to see #738 if we don't merge it sooner.

@yob
Copy link
Contributor Author

yob commented Feb 10, 2021

Thanks all - list updated

@jdub
Copy link
Contributor

jdub commented Feb 10, 2021

If you're doing SecurityGroupIds, perhaps ManagedPolicyARNs? Just discovered it. 😆

@nitrocode
Copy link
Contributor

@chloeruka that wouldn't be a breaking change since ssh access would still be available just through ssm instead of port 22.

If it's not a breaking change, could it be added prior to a 6.0 release?

@chloeruka
Copy link
Contributor

It's not so much the availability of equivalent/replacement features, but removal of parameters that would make us consider it more appropriate for a major version. Changing things around might require users adjust parameters or automation surrounding their stacks. We want low friction Cloudformation upgrades since it's currently tied to Agent updates.

@nitrocode
Copy link
Contributor

I'd like to second the docker 20.x upgrade as that would allow us to no longer have to set environment variables DOCKER_EXPERIMENTAL and DOCKER_CLI_EXPERIMENTAL which would deprecate the EnableDockerExperimental parameter on the stack.

@triarius
Copy link
Contributor

v6 is out, so I'm going to close this.

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

No branches or pull requests

6 participants