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

Add release blog post for FerretDB v1.22.0 #4401

Merged
merged 6 commits into from
Jun 27, 2024
Merged

Conversation

Fashander
Copy link
Member

Description

Readiness checklist

  • I added/updated unit tests (and they pass).
  • I added/updated integration/compatibility tests (and they pass).
  • I added/updated comments and checked rendering.
  • I made spot refactorings.
  • I updated user documentation.
  • I ran task all, and it passed.
  • I ensured that PR title is good enough for the changelog.
  • (for maintainers only) I set Reviewers (@FerretDB/core), Milestone (Next), Labels, Project and project's Sprint fields.
  • I marked all done items in this checklist.

@Fashander Fashander added the blog/marketing Marketing (and releases) blog posts label Jun 27, 2024
@Fashander Fashander added this to the v1.23.0 milestone Jun 27, 2024
@Fashander Fashander requested a review from a team June 27, 2024 13:04
@Fashander Fashander self-assigned this Jun 27, 2024
@Fashander Fashander marked this pull request as ready for review June 27, 2024 13:04
@Fashander Fashander enabled auto-merge (squash) June 27, 2024 13:04
Copy link
Contributor

mergify bot commented Jun 27, 2024

Marketing blog posts should be reviewed by @ptrfarkas and @AlekSi.

Copy link

codecov bot commented Jun 27, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.03%. Comparing base (300fbc3) to head (0fe3132).

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #4401      +/-   ##
==========================================
+ Coverage   73.93%   74.03%   +0.09%     
==========================================
  Files         323      323              
  Lines       22398    22398              
==========================================
+ Hits        16561    16582      +21     
+ Misses       4620     4607      -13     
+ Partials     1217     1209       -8     

see 10 files with indirect coverage changes

Flag Coverage Δ
filter-true 67.41% <ø> (+0.04%) ⬆️
hana-1 0.00% <ø> (ø)
integration 67.41% <ø> (+0.04%) ⬆️
mongodb-1 5.05% <ø> (ø)
postgresql-1 43.93% <ø> (-0.02%) ⬇️
postgresql-2 45.00% <ø> (+0.12%) ⬆️
postgresql-3 43.00% <ø> (ø)
postgresql-4 40.27% <ø> (+<0.01%) ⬆️
postgresql-5 43.75% <ø> (+0.02%) ⬆️
sqlite-1 43.18% <ø> (+0.02%) ⬆️
sqlite-2 44.04% <ø> (-0.05%) ⬇️
sqlite-3 42.22% <ø> (ø)
sqlite-4 39.41% <ø> (-0.01%) ⬇️
sqlite-5 ?
unit 33.04% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

@AlekSi AlekSi added the trust PRs that can access Actions secrets label Jun 27, 2024
Here's how you can do it:

```sh
ferretdb --test-enable-new-auth=true --setup-timeout=1m --setup-username=user --setup-password=pass --setup-database=ferretdb
Copy link
Member

Choose a reason for hiding this comment

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

Let's drop timeout for simplicity; the default (30s) is good enough

- `--setup-username`/`FERRETDB_SETUP_USERNAME`: Specifies the username to be created.
- `--setup-password`/`FERRETDB_SETUP_PASSWORD`: Specifies the password for the user (can be empty).
- `--setup-timeout`/`FERRETDB_SETUP_TIMEOUT`: Sets the timeout for establishing a working backend connection.
- `--setup-database`/`FERRETDB_SETUP_DATABASE`: Specifies the database to create the user in.
Copy link
Member

Choose a reason for hiding this comment

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

Let's say initial database that will be created.
(because that user is not created in this database, but in the admin database for that setup)

- `--setup-database`/`FERRETDB_SETUP_DATABASE`: Specifies the database to create the user in.
- `--test-enable-new-auth`/`FERRETDB_TEST_ENABLE_NEW_AUTH`: Must be set to `true` to enable the new authentication setup.

Once the flags/environment variables are passed, FerretDB will create the specified user with the given password.
Copy link
Member

Choose a reason for hiding this comment

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

and the given database

- `--setup-database`/`FERRETDB_SETUP_DATABASE`: Specifies the initial database that will be created.
- `--test-enable-new-auth`/`FERRETDB_TEST_ENABLE_NEW_AUTH`: Must be set to `true` to enable the new authentication setup.

Once the flags/environment variables are passed, FerretDB will create the specified user with the given password and database.
Copy link
Member

Choose a reason for hiding this comment

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

It does not create a user with a given [...] database

Copy link
Member Author

Choose a reason for hiding this comment

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

So something like this: Once the flags/environment variables are passed, FerretDB will create the specified user with the given password and the given database.?

@AlekSi AlekSi disabled auto-merge June 27, 2024 14:47
@AlekSi AlekSi merged commit ee7a8b1 into FerretDB:main Jun 27, 2024
29 of 33 checks passed
@AlekSi AlekSi changed the title Add release blog post for FerretDB v.1.22.0 Add release blog post for FerretDB v1.22.0 Jul 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blog/marketing Marketing (and releases) blog posts trust PRs that can access Actions secrets
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants