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

Additional security rules for NSGs are not applied properly for Azure #942

Closed
seriva opened this issue Feb 26, 2020 · 0 comments
Closed
Assignees
Labels

Comments

@seriva
Copy link
Collaborator

seriva commented Feb 26, 2020

When specifying additional security rules for a VM they are not applied correctly for the NSG.

@seriva seriva self-assigned this Feb 26, 2020
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
@seriva seriva closed this as completed Feb 26, 2020
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
Labels
Projects
None yet
Development

No branches or pull requests

1 participant