Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: cloudquery/cloudquery
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: cli-v1.1.4
Choose a base ref
...
head repository: cloudquery/cloudquery
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: cli-v1.1.5
Choose a head ref
  • 8 commits
  • 47 files changed
  • 4 contributors

Commits on Oct 16, 2022

  1. chore: Update plugin destination-postgresql version to v1.3.3 (#2893) 

    Updates the `destination-postgresql` plugin latest version to v1.3.3
    @cq-bot
    cq-bot authored Oct 16, 2022
    Configuration menu
    Copy the full SHA
    aeee463 View commit details
    Browse the repository at this point in the history

  2. feat(aws): Glacier resources (#2703) 

    Implements #2583
    @disq
    disq authored Oct 16, 2022
    Configuration menu
    Copy the full SHA
    34e9f61 View commit details
    Browse the repository at this point in the history

  3. chore: Update CLI version to v1.1.4 (#2895) 

    Updates the CLI latest version to v1.1.4
    @cq-bot
    cq-bot authored Oct 16, 2022
    Configuration menu
    Copy the full SHA
    fe827b2 View commit details
    Browse the repository at this point in the history

  4. chore(main): Release plugins-source-aws v3.0.0 (#2830) 

    🤖 I have created a release *beep* *boop*
---


## [3.0.0](plugins-source-aws-v2.5.2...plugins-source-aws-v3.0.0) (2022-10-16)


### ⚠ BREAKING CHANGES

* More tag cleanup (#2837)

### Features

* **aws:** CQ Policies to Validate IMDSv2 Usage and Enforcement across EC2, Lightsail, and AMIs ([#2807](#2807)) ([31d4f79](31d4f79))
* **aws:** Glacier resources ([#2703](#2703)) ([34e9f61](34e9f61)), closes [#2583](#2583)


### Bug Fixes

* **aws:** Clean up tag fields ([#2776](#2776)) ([d071a0e](d071a0e))
* **deps:** Update plugin-sdk for aws to v0.13.8 ([#2848](#2848)) ([14e2571](14e2571))
* More tag cleanup ([#2837](#2837)) ([e781491](e781491)), closes [#2836](#2836)
* Update endpoints ([#2831](#2831)) ([a3b289c](a3b289c))
* Update endpoints ([#2890](#2890)) ([2d3b885](2d3b885))

---
This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
    @cq-bot
    cq-bot authored Oct 16, 2022
    Configuration menu
    Copy the full SHA
    0ebac87 View commit details
    Browse the repository at this point in the history

  5. fix(cli): Deprecate color flag (#2812) 

    
#### Summary

Related to #2644.
Since the default is to have log color, it makes sense to have a `--no-color` flag instead of `--color`. I added one in a backwards compatible way. Also I think `auto` never really worked.

<!--
    @erezrokah
    erezrokah authored Oct 16, 2022
    Configuration menu
    Copy the full SHA
    9565195 View commit details
    Browse the repository at this point in the history

  6. fix: Add codegen for AWS regions (#2701) 

    Found another case of an AWS resource not being generated with codegen. It was unfortunately not so easy to deal with this one in a backwards-compatible way. The biggest issue is keeping the name `aws_regions` rather than `aws_ec2_regions` (which would be in line with all other resources). 

Note: This could perhaps be considered a `chore`, as it should change no user-facing functionality, but since there is a small change in the ordering of the columns I think I'd rather have it reported as one of the changes in the next release.
    @hermanschaaf
    hermanschaaf authored Oct 16, 2022
    Configuration menu
    Copy the full SHA
    9b1b2ca View commit details
    Browse the repository at this point in the history

  7. chore(release): Ensure only 1 release please workflow runs at the sam… 

    …e time (#2896)



#### Summary

Having multiple release please workflows running at the same time can lead to race conditions where 2 workflows think they need to create release PRs.

This change ensures only one runs at the same time, visit https://docs.github.com/en/actions/using-jobs/using-concurrency for more information.

This issue is more evident in the monorepo where release please takes longer to process all releases. In small repos it's fast enough so this is not an issue

<!--
    @erezrokah
    erezrokah authored Oct 16, 2022
    Configuration menu
    Copy the full SHA
    b4a9f67 View commit details
    Browse the repository at this point in the history

  8. chore(main): Release cli v1.1.5 (#2897) 

    🤖 I have created a release *beep* *boop*
---


## [1.1.5](cli-v1.1.4...cli-v1.1.5) (2022-10-16)


### Bug Fixes

* **cli:** Deprecate color flag ([#2812](#2812)) ([9565195](9565195))

---
This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
    @cq-bot
    cq-bot authored Oct 16, 2022
    Configuration menu
    Copy the full SHA
    81259e5 View commit details
    Browse the repository at this point in the history
Loading