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

Warning we will deprecate Azure Targets in 3.4 #2401

Closed
4 tasks
michaelnoonan opened this issue Feb 29, 2016 · 4 comments
Closed
4 tasks

Warning we will deprecate Azure Targets in 3.4 #2401

michaelnoonan opened this issue Feb 29, 2016 · 4 comments
Assignees
Labels
kind/enhancement This issue represents an enhancement we are committed to adding to Octopus as some time
Milestone

Comments

@michaelnoonan
Copy link
Contributor

michaelnoonan commented Feb 29, 2016

  • Blog post explaining we will deprecate Azure Targets in 3.4
  • Dismissable warning on Environments page if using an Azure Targets
  • More specific warning on new Deployment Target page
  • Warning message when deploying to an Azure target
@michaelnoonan michaelnoonan added the kind/enhancement This issue represents an enhancement we are committed to adding to Octopus as some time label Feb 29, 2016
@michaelnoonan
Copy link
Contributor Author

We want to make sure there's a good answer for Regions in Azure without Azure Deployment Targets before doing this.

@vanessalove
Copy link
Contributor

vanessalove commented Jun 30, 2016

Updated decision on what to do:

  • documentation on how to move from Azure targets
  • log warning in the deployment when using Azure targets

@vanessalove vanessalove added this to the 3.4.0 milestone Jun 30, 2016
@vanessalove
Copy link
Contributor

Also logged in the trello - but this is for the warning release notes

@lock
Copy link

lock bot commented Nov 25, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Nov 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/enhancement This issue represents an enhancement we are committed to adding to Octopus as some time
Projects
None yet
Development

No branches or pull requests

4 participants