Ansible namespace support flow #539
Conversation
Docker is ratelimiting the RH network. It happesn quite often in the office on the VPN network
|
@Hyperkid123 Looking good!
|
Looks like they canned the fun one (its half baked anyway). He chose the right one |
| - unable to get to my ansible namespace | ||
| - i used to be able to access my ansible namespace but i can't anymore | ||
| - are you able to get me access to a ansible namespace | ||
| - it says i don't have access to my ansible namespace |
There was a problem hiding this comment.
| - it says i don't have access to my ansible namespace | |
| - it says i don't have access to my ansible namespace | |
| - ansible namespace access | |
| - ansible namespace issues | |
| - ansible namespace problems | |
| - ansible namespace doesn't work | |
| - how do I get access to an ansible namespace | |
| - fix ansible namespace |
Our bot is dumb, some more examples
data/ansible/domain.yml
Outdated
| slots: {} | ||
|
|
||
| responses: | ||
| utter_inform_reach_out_to_support: |
There was a problem hiding this comment.
| utter_inform_reach_out_to_support: | |
| utter_ansible_inform_reach_out_to_support: |
Just want to scope these. I don't know we would manage to duplicate the name elsewhere, but you never know
data/ansible/rules.yml
Outdated
| - rule: Reach out to support | ||
| steps: | ||
| - intent: intent_ansible_namespaces_access_issues | ||
| - action: utter_inform_reach_out_to_support |
There was a problem hiding this comment.
| - action: utter_inform_reach_out_to_support | |
| - action: utter_ansible_inform_reach_out_to_support |
|
@tahmidefaz @justinorringer Thanks for checking this over. I'll update the config files. And yeah I was a bit confused about the missing actions. I am glad that I did not misrepresent the miro board. |
Hyperkid123
force-pushed
the
ansible-namespace-support-flow
branch
from
bba5935
to
4c5885c
Compare
Why would they keep it there if they deprecated it... 🤦 |
Hyperkid123
force-pushed
the
ansible-namespace-support-flow
branch
from
4001ee3
to
8f53a71
Compare
Jira: https://issues.redhat.com/browse/RHCLOUD-32338
In addition to the required changes, I've also done some extra stuff. Let me know if you want to split it into a different PR