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

Makes possible to attach additional or replace default security groups to subnets #96

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

JanisOrlovs
Copy link

Makes possible to attach additional or replace default security groups to subnets

Previously worked only with the default security group

Signed-off-by: janis.orlovs [email protected]

Proposed change

Makes possible to attach additional or replace default security groups to subnets

Previously worked only with the default security group

How has these changes been tested?

Test deployments works on my location

Automated testing

NA

Manual testing

If no automated testing is run, please ensure that at least the three steps below are passing without any error.

  • run terraform apply
  • add security group ID based on variables
  • terraform destroy

Checklist before submitting your PR

  • My code follows the style guidelines of this project
  • these changes provision new resources:
    • I have updated the README introduction section (README.adoc)
    • I have updated the README introduction section (README.md)
  • these changes adds any new variables:
  • I have updated the changelog to include an entry for these changes
  • I have updated all provided examples, including each README file and all applicable code blocks
  • these changes generates no new warnings
  • Any dependent changes have been merged and published in upstream modules

Note: If you are not an Oracle employee, to contribute to an Oracle-sponsored open-source project, you need to sign the Oracle Contributor Agreement (OCA).

… for subnets.

Previously worked only with default security group

Signed-off-by: janis.orlovs <[email protected]>
@JanisOrlovs
Copy link
Author

Hello,

Any options to merge this?

@hyder
Copy link
Contributor

hyder commented Sep 6, 2022

Hi @JanisOrlovs,

Very sorry for the delay.

@JanisOrlovs
Copy link
Author

Hello,
Any progress on this?

@JanisOrlovs
Copy link
Author

Hello,
Is there movent on this?

@JanisOrlovs
Copy link
Author

Hello,
This is not serious.

@snafuz
Copy link
Contributor

snafuz commented Sep 13, 2022

Hi @JanisOrlovs - I'm very sorry for the delay. I'm reviewing your submission now and will provide feedback in the next couple of days

@@ -0,0 +1,3 @@
data "oci_core_vcn" "vcn_this" {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this datasource is not used anywhere and should be removed

@@ -102,4 +102,5 @@ attached_drg_id = null
#subnets = {
# sub1 = {name = "subnet1",cidr_block = "10.0.4.0/24"}
# sub2 = {cidr_block="10.0.5.0/24",type="private"}
# sub3 = {cidr_block="10.0.6.0/24",type="private", security_list_ids=["ocid1.securitylist.oc1.eu-frankfurt-1.aaaa","ocid1.securitylist.oc1.eu-frankfurt-1.bbbb"]}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The subnet module is a submodule of vcn module. The security list must be created inside the VCN to be assigned to any subnet. Hence you can not have security lists created previous to the VCN itself. How do you intend to use this feature in a real scenario?

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

Successfully merging this pull request may close these issues.

3 participants