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

Deploy: Release v1.4.3 #376

Merged
merged 1 commit into from
Jan 21, 2024
Merged

Deploy: Release v1.4.3 #376

merged 1 commit into from
Jan 21, 2024

Conversation

magneticstain
Copy link
Owner

PR Summary

Add new Dockerfile for releases. This is to be in line with goreleaser reqs.

Related Issue(s)

Related to #367

This is to be in line with goreleaser reqs
@magneticstain magneticstain added the release Issue or PR detailing a specific, versioned release label Jan 21, 2024
@magneticstain magneticstain self-assigned this Jan 21, 2024
Copy link

codacy-production bot commented Jan 21, 2024

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation Diff coverage
+0.00% (target: -2.00%)
Coverage variation details
Coverable lines Covered lines Coverage
Common ancestor commit (0ed8b71) 709 465 65.59%
Head commit (5643c8a) 1418 (+709) 930 (+465) 65.59% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details
Coverable lines Covered lines Diff coverage
Pull request (#376) 0 0 ∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

You may notice some variations in coverage metrics with the latest Coverage engine update. For more details, visit the documentation

@magneticstain magneticstain merged commit f0cc93a into main Jan 21, 2024
11 checks passed
magneticstain added a commit that referenced this pull request Jan 21, 2024
* Bump to trigger container release (#373)

* Update version

* Update version in "Commits since" badge

* Deploy: Release v1.4.2 (#375)

* Minor: Update app versions

* Switch to goreleaser for container image deploy (#374)

* Remove current container deploy workflow config

* Update goreleaser config and relase workflow for docker release support

* Add new Dockerfile for releases (#376)

This is to be in line with goreleaser reqs

* Migrate from docker/login-action to custom script for registry auth

Required as docker-login-action doesn't support multi-registry authentication.

* Minor: Update versions

* Revert migration from login-action to custom

I misunderstood the github action logs :(

* Update Job Permissions to Remove Content:Read Permission

This was overriding the globally-set Content:Write permission.
This caused the GHAW for releases to fail to create a release
magneticstain added a commit that referenced this pull request Jan 25, 2024
* Bump to trigger container release (#373)

* Update version

* Update version in "Commits since" badge

* Deploy: Release v1.4.2 (#375)

* Minor: Update app versions

* Switch to goreleaser for container image deploy (#374)

* Remove current container deploy workflow config

* Update goreleaser config and relase workflow for docker release support

* Add new Dockerfile for releases (#376)

This is to be in line with goreleaser reqs

* Migrate from docker/login-action to custom script for registry auth

Required as docker-login-action doesn't support multi-registry authentication.

* Deploy: Release v1.4.5 (#377)

* Minor: Update versions

* Revert migration from login-action to custom

I misunderstood the github action logs :(

* Update Job Permissions to Remove Content:Read Permission

This was overriding the globally-set Content:Write permission.
This caused the GHAW for releases to fail to create a release

* Issue 383 add service to user output (#384)

* Add `CloudSvc` as a attribute of `Resource()`

* Add CloudSvc Value to Output For Found Resource

* Set CloudSvc in All Supported Resource Plugins

* Minor: Fix typo in found resource user output

* Minor: update app version
magneticstain added a commit that referenced this pull request Feb 21, 2024
* Bump to trigger container release (#373)

* Update version

* Update version in "Commits since" badge

* Deploy: Release v1.4.2 (#375)

* Minor: Update app versions

* Switch to goreleaser for container image deploy (#374)

* Remove current container deploy workflow config

* Update goreleaser config and relase workflow for docker release support

* Add new Dockerfile for releases (#376)

This is to be in line with goreleaser reqs

* Migrate from docker/login-action to custom script for registry auth

Required as docker-login-action doesn't support multi-registry authentication.

* Deploy: Release v1.4.5 (#377)

* Minor: Update versions

* Revert migration from login-action to custom

I misunderstood the github action logs :(

* Update Job Permissions to Remove Content:Read Permission

This was overriding the globally-set Content:Write permission.
This caused the GHAW for releases to fail to create a release

* Issue 383 add service to user output (#384)

* Add `CloudSvc` as a attribute of `Resource()`

* Add CloudSvc Value to Output For Found Resource

* Set CloudSvc in All Supported Resource Plugins

* Minor: Fix typo in found resource user output

* Minor: update app version

* Minor: Update APP_ENV and APP_VER

* Fix help menu (#402)

* Update `ipaddr` notes to fix default value and note it's a required param

* Remove unneeded default clauses from cli help menu

* Fix `svc` help message
magneticstain added a commit that referenced this pull request Feb 21, 2024
* Minor: Updates for new version

* Minor: Sync w/ Release v1.4.5 (#378)

* Bump to trigger container release (#373)

* Update version

* Update version in "Commits since" badge

* Deploy: Release v1.4.2 (#375)

* Minor: Update app versions

* Switch to goreleaser for container image deploy (#374)

* Remove current container deploy workflow config

* Update goreleaser config and relase workflow for docker release support

* Add new Dockerfile for releases (#376)

This is to be in line with goreleaser reqs

* Migrate from docker/login-action to custom script for registry auth

Required as docker-login-action doesn't support multi-registry authentication.

* Minor: Update versions

* Revert migration from login-action to custom

I misunderstood the github action logs :(

* Update Job Permissions to Remove Content:Read Permission

This was overriding the globally-set Content:Write permission.
This caused the GHAW for releases to fail to create a release

* Move app environment value to main

This will bring it next to the app version value, which means only one location to visit to update for releases.

* Issue 383 add service to user output (#384)

* Add `CloudSvc` as a attribute of `Resource()`

* Add CloudSvc Value to Output For Found Resource

* Set CloudSvc in All Supported Resource Plugins

* Minor: Fix typo in found resource user output

* Minor: update app version

* Minor: Sync Release v1.4.6 w v2.0.0 Branch (#386)

* Bump to trigger container release (#373)

* Update version

* Update version in "Commits since" badge

* Deploy: Release v1.4.2 (#375)

* Minor: Update app versions

* Switch to goreleaser for container image deploy (#374)

* Remove current container deploy workflow config

* Update goreleaser config and relase workflow for docker release support

* Add new Dockerfile for releases (#376)

This is to be in line with goreleaser reqs

* Migrate from docker/login-action to custom script for registry auth

Required as docker-login-action doesn't support multi-registry authentication.

* Deploy: Release v1.4.5 (#377)

* Minor: Update versions

* Revert migration from login-action to custom

I misunderstood the github action logs :(

* Update Job Permissions to Remove Content:Read Permission

This was overriding the globally-set Content:Write permission.
This caused the GHAW for releases to fail to create a release

* Issue 383 add service to user output (#384)

* Add `CloudSvc` as a attribute of `Resource()`

* Add CloudSvc Value to Output For Found Resource

* Set CloudSvc in All Supported Resource Plugins

* Minor: Fix typo in found resource user output

* Minor: update app version

* Minor: Fix APP_ENV and app version from 1.4.6 sync

* Add Official Windows Support (#389)

* Add GA workflow for building on windows for each PR to this branch

Needed for siloed testing.

* Minor: Bump for testing (#388)

* Bump for testing

* Remove `coverprofile` param from go test build step for testing

* Update go test step for testing

* Update utils unit test to be more verbose

* Fix coverage file filename in upload build step

* Update coverage filename for all coverage build steps

* Update utils unit test to be more verbose

* Exclude utils unit tests from running on windows OS

For some reason, Github Actions windows runners don't resolve to IPv6 addresses

* Update README to note official Windows support

* Remove test build workflow config

* Add Windows to main build workflow

* Update `go test` command in codavy coverage reporter build workflow

While not required, it brings it into line with other build workflows

* Minor: Update APP_ENV and APP_VER

* Fix help menu (#402)

* Update `ipaddr` notes to fix default value and note it's a required param

* Remove unneeded default clauses from cli help menu

* Fix `svc` help message

* Minor: Fix syntax of code coverage build step
magneticstain added a commit that referenced this pull request Mar 4, 2024
* Minor: Updates for new version

* Minor: Sync w/ Release v1.4.5 (#378)

* Bump to trigger container release (#373)

* Update version

* Update version in "Commits since" badge

* Deploy: Release v1.4.2 (#375)

* Minor: Update app versions

* Switch to goreleaser for container image deploy (#374)

* Remove current container deploy workflow config

* Update goreleaser config and relase workflow for docker release support

* Add new Dockerfile for releases (#376)

This is to be in line with goreleaser reqs

* Migrate from docker/login-action to custom script for registry auth

Required as docker-login-action doesn't support multi-registry authentication.

* Minor: Update versions

* Revert migration from login-action to custom

I misunderstood the github action logs :(

* Update Job Permissions to Remove Content:Read Permission

This was overriding the globally-set Content:Write permission.
This caused the GHAW for releases to fail to create a release

* Move app environment value to main

This will bring it next to the app version value, which means only one location to visit to update for releases.

* Minor: Sync Release v1.4.6 w v2.0.0 Branch (#386)

* Bump to trigger container release (#373)

* Update version

* Update version in "Commits since" badge

* Deploy: Release v1.4.2 (#375)

* Minor: Update app versions

* Switch to goreleaser for container image deploy (#374)

* Remove current container deploy workflow config

* Update goreleaser config and relase workflow for docker release support

* Add new Dockerfile for releases (#376)

This is to be in line with goreleaser reqs

* Migrate from docker/login-action to custom script for registry auth

Required as docker-login-action doesn't support multi-registry authentication.

* Deploy: Release v1.4.5 (#377)

* Minor: Update versions

* Revert migration from login-action to custom

I misunderstood the github action logs :(

* Update Job Permissions to Remove Content:Read Permission

This was overriding the globally-set Content:Write permission.
This caused the GHAW for releases to fail to create a release

* Issue 383 add service to user output (#384)

* Add `CloudSvc` as a attribute of `Resource()`

* Add CloudSvc Value to Output For Found Resource

* Set CloudSvc in All Supported Resource Plugins

* Minor: Fix typo in found resource user output

* Minor: update app version

* Minor: Fix APP_ENV and app version from 1.4.6 sync

* Add Official Windows Support (#389)

* Add GA workflow for building on windows for each PR to this branch

Needed for siloed testing.

* Minor: Bump for testing (#388)

* Bump for testing

* Remove `coverprofile` param from go test build step for testing

* Update go test step for testing

* Update utils unit test to be more verbose

* Fix coverage file filename in upload build step

* Update coverage filename for all coverage build steps

* Update utils unit test to be more verbose

* Exclude utils unit tests from running on windows OS

For some reason, Github Actions windows runners don't resolve to IPv6 addresses

* Update README to note official Windows support

* Remove test build workflow config

* Add Windows to main build workflow

* Update `go test` command in codavy coverage reporter build workflow

While not required, it brings it into line with other build workflows

* Deploy: Sync w/ Release v1.4.7 (#404)

* Bump to trigger container release (#373)

* Update version

* Update version in "Commits since" badge

* Deploy: Release v1.4.2 (#375)

* Minor: Update app versions

* Switch to goreleaser for container image deploy (#374)

* Remove current container deploy workflow config

* Update goreleaser config and relase workflow for docker release support

* Add new Dockerfile for releases (#376)

This is to be in line with goreleaser reqs

* Migrate from docker/login-action to custom script for registry auth

Required as docker-login-action doesn't support multi-registry authentication.

* Deploy: Release v1.4.5 (#377)

* Minor: Update versions

* Revert migration from login-action to custom

I misunderstood the github action logs :(

* Update Job Permissions to Remove Content:Read Permission

This was overriding the globally-set Content:Write permission.
This caused the GHAW for releases to fail to create a release

* Issue 383 add service to user output (#384)

* Add `CloudSvc` as a attribute of `Resource()`

* Add CloudSvc Value to Output For Found Resource

* Set CloudSvc in All Supported Resource Plugins

* Minor: Fix typo in found resource user output

* Minor: update app version

* Minor: Update APP_ENV and APP_VER

* Fix help menu (#402)

* Update `ipaddr` notes to fix default value and note it's a required param

* Remove unneeded default clauses from cli help menu

* Fix `svc` help message

* Minor: Fix App Metadata

* Feature: Add GCP Support (#424)

* Refactor code to support multiple platforms (#405)

* Refactor code to support multiple platforms

- Directory structure updated
- Forward method added to allow searches by platform

* Minor: Fix App Metadata

* Add support for gcp compute vms (#419)

* Refactor `search` package to be more decoupled from AWS module

* Split `search` to its own module, separate from aws

* Abstract out platform connection management

* Migrate `SearchAWSSvc` from `search` to `awscontroller` package

* Migrate `FetchOrgAcctIds` from `search` to `awscontroller` package

* Add GCP Plugin

- Create new plugin package for gcp, including supporting libs
- Update code to be more decoupled in order to support a larger variety of plugins

* Multiple Update to Fix Memory Management Issues

* Update go.mod

* Fix issue w/ ip fuzzing service set

- Struct service set was being updated instead of local `svcSet`

* Test: Add/update unit tests for awscontroller and `search`

* Test: Add unit tests for GCP controller package

* Test: Add unit tests for `compute` plugin

* Test: Fix `TestRunIPFuzzing_AdvancedFuzzing` in `search` unit tests

* Add load balancing plugin (#422)

* Add load balancing plugin

* Test: Add `load_balancing` service option to SearchGCPSvc() unit test

* Test: Write unit tests for `CheckComputeIP()`

* Move IP version determination function to utils package

* Add gcp cloudsql support (#423)

* Add initial plugin code for CloudSQL

* Add CloudSQL plugin

* Test: Add unit test for CloudSQL plugin

* Enable cloud_sql service for searching

* Add `cloud_sql` service to search unit test for service reconciliation

* Minor: Fix formatting issues

* Check off "GCP Support" in README

* Deploy: doc updates for release

* Docs: Update help menu in README

* Minor: formatting fix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release Issue or PR detailing a specific, versioned release
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

1 participant