You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, with the gcp_projects is possible to filter by project_id; project_name and project_number.
In a scenario where one is verifying the state of resources and the project name is like /^foo/, but there are two projects called foo with one of them scheduled for deletion, that will cause tests to fail because:
But that's not a real failure, as something that does not exist anymore can't be tested.
It would be great to have the ability to filter by project status. Or completely discard projects which are not active (therefore not implementing the filter at all).
Does that make sense?
What do you think?
The text was updated successfully, but these errors were encountered:
Note, the above was raised because I don't necessarily know (and/or want to) the project id of a project (which may be randomly generated). But I do know the project name (provided it follows a certain naming convention).
For example:
gcp_project_name: my-project
Then with some automation that creates projects with semi-random ids, like so:
gcp_project_id: "{{ gcp_project_name }}-{{ 9999999 | random }}"
The above has been "Ansible-ified", but I think you get the idea 😄
At the moment, with the gcp_projects is possible to filter by project_id; project_name and project_number.
In a scenario where one is verifying the state of resources and the project name is like
/^foo/
, but there are two projects calledfoo
with one of them scheduled for deletion, that will cause tests to fail because:But that's not a real failure, as something that does not exist anymore can't be tested.
It would be great to have the ability to filter by project status. Or completely discard projects which are not active (therefore not implementing the filter at all).
Does that make sense?
What do you think?
The text was updated successfully, but these errors were encountered: