Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
If a tenant is passed to the URL after clicking deploy, we should not pre-fill tenant tags from the release channel. #4322
Currently if you select to deploy to a Tenant from the project overview the Tenant Tags associated with the releases channel are pre-filled. This can cause you to accidentally deploy to multiple tenants when only selecting a single tenant to deploy to.
We should not pre-fill any tenant tags when the tenant is already defined in the URL.
Steps to replicate:
Create a Tenant tag-set with two tags.
Set up a simple Tenanted project.
You will find that the Channels tags for both Tenant-A & Tenant-B are pre-selected, alongside the Tenant you have selected to deploy, as this is already defined in the URL.
On this page the URL has defined which tenants to deploy and auto populated that field, the channels tenant tags should not auto fill as this by default will deploy Tenant-A & Tenant-B if you do not notice.
Add a Tenant tag C. Scope tag C to Tenant-A. (Tenant-A should have two tags now A&C.)