Skip to content

Support value_specs for Ports#2535

Closed
lentzi90 wants to merge 1 commit intogophercloud:masterfrom
Nordix:lentzi90/port-value-specs
Closed

Support value_specs for Ports#2535
lentzi90 wants to merge 1 commit intogophercloud:masterfrom
Nordix:lentzi90/port-value-specs

Conversation

@lentzi90
Copy link
Copy Markdown
Contributor

@lentzi90 lentzi90 commented Jan 18, 2023

Fixes #2532

Links to the line numbers/files in the OpenStack source code that support the
code in this PR:

Docs: https://docs.openstack.org/heat/zed/template_guide/openstack.html#OS::Neutron::Port-prop-value_specs

Copy link
Copy Markdown

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Thank you for submitting your first PR! Be sure that we will be looking at it but keep in mind
this sometimes takes a while.
Please let the maintainers know if your PR has not got enough attention after a few days.
If any doubt, please consult our PR tutorial.

@coveralls
Copy link
Copy Markdown

Coverage Status

Coverage: 80.086%. Remained the same when pulling d3b6dec on Nordix:lentzi90/port-value-specs into a4c3a15 on gophercloud:master.

DeviceOwner *string `json:"device_owner,omitempty"`
SecurityGroups *[]string `json:"security_groups,omitempty"`
AllowedAddressPairs *[]AddressPair `json:"allowed_address_pairs,omitempty"`
ValueSpecs map[string]string `json:"value_specs,omitempty"`
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I know it's horrible, but could you please change this field to be a pointer?
Before your change, UpdateOpts is comparable. Having it as a pointer would keep it comparable, and thus would not break compilation of any consumer code.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Good point, done!

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Argh... messed up the branches. go mod does not like branches with / in the name, and I'm using the branch here for a PR in CAPO (kubernetes-sigs/cluster-api-provider-openstack#1452), which means I had to change the branch name.
I will create a new PR with the correct branch name.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Ok, thanks! I am closing this one to avoid confusion.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

The new PR is #2537. It has the same content (with the fixed the pointer). Sorry for the mess.

Ref for go issue with slashes in branch names: golang/go#32955 (comment)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Good to know!

@lentzi90 lentzi90 deleted the lentzi90/port-value-specs branch January 24, 2023 13:38
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.

Enhancement: Support value_specs for ports

3 participants