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

Using Filter Deployment Name #22

Closed
KZeronimo opened this issue Feb 3, 2019 · 1 comment
Closed

Using Filter Deployment Name #22

KZeronimo opened this issue Feb 3, 2019 · 1 comment

Comments

@KZeronimo
Copy link

Hi - I've been using this task to successfully capture ARM outputs - I decided to "test" the filter deployment (I really don't have concurrent ARM deployments going on in the same rg - I do have some nested templates and the remaining ARM deployments are sequential so I have a capture ARM outputs after each deploy ARM step) - I used the name of my template file ie foo.json I entered foo in the Filter Deployment Name - I ran two successful deployments and both time I encountered the following

screen shot 2019-02-03 at 5 02 05 pm

Any idea what I'm doing incorrectly?

Thanks in advance

@keesschollaart81
Copy link
Owner

Maybe. This is a breaking change between v4 and v5. In the most recent version of ARM Outputs I use micromatch as the matching algoritm so you need to use * for wildcard searches or an exact match (case insensitive). I've updated the info-tooltip with this info. Does this fix your issue?

keesschollaart81 added a commit that referenced this issue Mar 3, 2019
* Now with v4 deprecation warning
* Support for MSI (#23) 
* Some more explanation for the deployment filter (#22)
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

2 participants