Skip to content

Conversation

@bfqrst
Copy link
Contributor

@bfqrst bfqrst commented Jul 16, 2021

Description

Default ports in Consul have changed over time.

Motivation and Context

In order to correctly generate rules for a Consul security group, this should be considered.

Breaking Changes

None that I know of.

How Has This Been Tested?

  • I have tested and validated these changes referencing my local branch in my Consul deployments, which worked as expected.

bfqrst and others added 5 commits July 15, 2021 15:42
Port 8400 for CLI disappeared along the way. In came 8501 for HTTPS and 8502 for gRPC.
feat: add gRPC and HTTPS ports to Consul array
@antonbabenko
Copy link
Member

@bryantbiggs When I clicked "Update branch" on the PR the commit 779c0bb is pushed to the master branch of the fork which triggers a GH Action for release. Is there a way to trigger Release only on the main repo and not for forks?

@antonbabenko antonbabenko merged commit 914bfad into terraform-aws-modules:master Nov 25, 2021
antonbabenko pushed a commit that referenced this pull request Nov 25, 2021
# [4.7.0](v4.6.1...v4.7.0) (2021-11-25)

### Features

* add gRPC and HTTPS ports to Consul array ([#223](#223)) ([914bfad](914bfad))
@antonbabenko
Copy link
Member

This PR is included in version 4.7.0 🎉

@bryantbiggs
Copy link
Member

@antonbabenko ya we could add in a hacky repo name check. however, unless users have the GH token set as a secret and as the same name, nothing will happen.

@antonbabenko
Copy link
Member

Ok, in the future let's add such a check to not even trigger anything. I propose that we track such issues somewhere in meta repository and apply them at once a bit later.

It is good that secrets are not floating around from the main repo to forks :)

antonbabenko added a commit to mbainter/terraform-aws-security-group that referenced this pull request Jan 10, 2022
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants