Additional security rules for NSGs are not applied properly for Azure #942
Assignees
Labels
Comments
Merged
seriva
added a commit
that referenced
this issue
Feb 26, 2020
Fixed addition of infrastructure documents when using --ful flag (#940) Switched from PyYAML to ruamel.yaml to preserve comments and commented out configs in the defaults. (#611) Fixed running epicli init -p any --full generating cloud sample configuration (#736) Checked if additional security rules for NSGs are applied properly for Azure (#942) Exclusion of SET_BY_AUTOMATION fields on generated configs Updated gen-licenses.py to use requirements.txt to generate licenses.py file instead of PipEnv
Merged
to-bar
pushed a commit
to to-bar/epiphany
that referenced
this issue
May 6, 2020
Fixed addition of infrastructure documents when using --ful flag (hitachienergy#940) Switched from PyYAML to ruamel.yaml to preserve comments and commented out configs in the defaults. (hitachienergy#611) Fixed running epicli init -p any --full generating cloud sample configuration (hitachienergy#736) Checked if additional security rules for NSGs are applied properly for Azure (hitachienergy#942) Exclusion of SET_BY_AUTOMATION fields on generated configs Updated gen-licenses.py to use requirements.txt to generate licenses.py file instead of PipEnv
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When specifying additional security rules for a VM they are not applied correctly for the NSG.
The text was updated successfully, but these errors were encountered: