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

QA work following the docs quickstart #198

Merged
merged 6 commits into from
Mar 16, 2020
Merged

QA work following the docs quickstart #198

merged 6 commits into from
Mar 16, 2020

Conversation

DimCitus
Copy link
Collaborator

@DimCitus DimCitus commented Mar 16, 2020

Follow the Quickstart and fix everything that we broke in the release making.

We want to use the environment value as a fallback when the user is not
providing us with --pgport, but we don't require the value to be there.
We need to change to be reflected so that the postgresql configuration file
we prepare contains the absolute path to the OpenSSL self-signed
certificate, when we create one.
Otherwise we get an error to create the startup.log file with the initial
logs from starting Postgres.
In particular we need to be careful about using --auth and --ssl-self-signed
options when creating the monitor and every other node.
@DimCitus DimCitus changed the base branch from master to release-1.2 March 16, 2020 14:07
@DimCitus DimCitus changed the title s QA work following the docs quickstart Mar 16, 2020
@DimCitus DimCitus requested review from JelteF and mtuncer March 16, 2020 14:07
@DimCitus DimCitus self-assigned this Mar 16, 2020
@DimCitus DimCitus added this to the pg_auto_failover 1.2 milestone Mar 16, 2020
@@ -578,11 +578,10 @@ monitor_config_set_setting(MonitorConfig *config,
bool
monitor_config_update_with_absolute_pgdata(MonitorConfig *config)
{
PostgresSetup pgSetup = config->pgSetup;
PostgresSetup *pgSetup = &(config->pgSetup);
Copy link
Contributor

Choose a reason for hiding this comment

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

change of behavior, instead of copy of the data we are working on the actual config. Is this intentional ?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

It is yeah, otherwise we don't use the absolute path and then we fail to use the proper PATH to the self-signed certificate that has been created when the users has given us a relative path to pgdata, such as --pgdata ./monitor as in the documentation.

@DimCitus DimCitus merged commit 13fbdff into release-1.2 Mar 16, 2020
@DimCitus DimCitus deleted the fix/docs-1.2 branch March 16, 2020 16:23
DimCitus added a commit that referenced this pull request Mar 19, 2020
* Don't error out when PGPORT does not exists in the environment.

We want to use the environment value as a fallback when the user is not
providing us with --pgport, but we don't require the value to be there.

* Forward the absolute PGDATA change.

We need to change to be reflected so that the postgresql configuration file
we prepare contains the absolute path to the OpenSSL self-signed
certificate, when we create one.

* Review the FOPEN_FLAGS_A to include O_RDWR.

Otherwise we get an error to create the startup.log file with the initial
logs from starting Postgres.

* Fix pg_autoctl show uri on the monitor.

* Quickstart review with the new code.

In particular we need to be careful about using --auth and --ssl-self-signed
options when creating the monitor and every other node.

* Adding compat write open mode O_TRUNC.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants