Skip to content
This repository has been archived by the owner on Feb 16, 2023. It is now read-only.

Release v0.24.0 #154

Merged
merged 74 commits into from
Nov 27, 2019
Merged

Release v0.24.0 #154

merged 74 commits into from
Nov 27, 2019

Conversation

SimonBarendse
Copy link
Member

@SimonBarendse SimonBarendse commented Nov 27, 2019

Added

mackenbach and others added 30 commits October 4, 2019 11:18
…ption

Update README onle-line description
 Update README examples to use new constructor and ReadString to develop
Add shorthand for generating random alphanumeric characters
Don't add a query parameter when no subject types are given.
These iterators make it possible to iterate over an infinite stream
of audit events. The events are fetched in batches (pages) from
the API, but this is abstracted away in the iterator.
This makes the logs easier to read, as the logs of downloading
the modules will be in a different component.
Cache go modules and download them in a different step in CI
Only add query params to request when not empty
The current paginator is not the right abstraction. There currently
is nothing generic about the paginator, which results in everything
being injected as functions.
Once we implement link headers, we can abstract away how we get the
URL of the next page, which is then done in the same way for all
pages.
Instead of waiting until a request is made, return the error when
constructing the client.
Now we don't go back and forth between strings and URLs.
Now this also doesn't return an error anymore.
SimonBarendse and others added 25 commits November 13, 2019 16:04
It works just like mkdir -p, creating all directories that do not
exist yet recursively and it does not error when the directories
already exist.
Add CreateAll func to dir service to create dirs recursively
Also, don't support filtering subject types just yet. We'll add
that later.
By doing so, we can remove the error from the constructor of the
iterator
We still have to add the subject type(s) filter before the full
functionality of ListEvents can be achieved with EventIterator.
Before then, we'll not deprecate ListEvents just yet.
Copy link
Member

@jpcoenen jpcoenen left a comment

Choose a reason for hiding this comment

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

@SimonBarendse SimonBarendse merged commit a2d07b0 into master Nov 27, 2019
@SimonBarendse SimonBarendse deleted the release/v0.24.0 branch November 27, 2019 12:44
Copy link
Member

@mackenbach mackenbach left a comment

Choose a reason for hiding this comment

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

I was just reading up on the changes and found two small things. @SimonBarendse could you have a quick look?

Also, could you walk me through the decision process for going with the AuditEventIteratorParams struct in person?

pkg/secrethub/repo.go Show resolved Hide resolved
//
// // Use event
// }
EventIterator(path string, _ *AuditEventIteratorParams) AuditEventIterator
Copy link
Member

Choose a reason for hiding this comment

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

Why do we have an unnamed parameter here? Would params be more descriptive?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, params as a name could also work.

The paramater is unnamed because it is not currently being used; there are no parameters to pass to the event iterator yet. The paramater is already added so that we can add parameters to the params struct without requiring a breaking change.

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