You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We'd love to accept your patches and contributions to this project.
3
-
We just ask that you follow our contribution guidelines when you do.
2
+
This project is community-driven, and we'd love to accept your patches and contributions.
3
+
We just ask that you follow our contribution guidelines when you do. Refer
4
+
to the [Contributor Handbook](https://sassoftware.github.io/contributor-handbook.html)
5
+
for guidance.
4
6
5
7
## Contributor License Agreement
6
8
Contributions to this project must be accompanied by a signed [Contributor Agreement](ContributorAgreement.txt).
7
-
You (or your employer) retain the copyright to your contribution; this simply grants us permission to use and redistribute your contributions as part of the project.
9
+
You (or your employer) retain the copyright to your contribution; this agreement simply grants
10
+
us permission to use and redistribute your contributions as part of the project.
8
11
9
-
## Code reviews
10
-
All submissions to this project—including submissions from project members—require review.
11
-
Our review process typically involves performing unit tests, development tests, integration tests, and security scans using internal SAS infrastructure.
12
-
For this reason, we don’t often merge pull requests directly from GitHub.
12
+
## Code Reviews
13
+
All submissions to this project—including submissions from project members—require
14
+
review. Our review process typically involves performing unit tests, development
15
+
tests, integration tests, and security scans.
13
16
14
-
Instead, we work with submissions internally first, vetting them to ensure they meet our security and quality standards.
15
-
We’ll do our best to work with contributors in public issues and pull requests; however, to ensure our code meets our internal compliance standards, we may need to incorporate your submission into a solution we push ourselves.
17
+
## Pull Request Requirement
18
+
All contributions (PRs) must be accompanied by passing unit and/or integration
19
+
tests, following our [testing philosophy](./docs/user/TestingPhilosophy.md). If you are unfamiliar with this process,
20
+
we are happy to help you navigate it by providing continuous collaboration within the pull request.
21
+
All pull requests must also pass our linter analysis checks. Contributions might
22
+
be subjected to security scans before they can be accepted.
16
23
17
-
This does not mean we don’t value or appreciate your contribution.
18
-
We simply need to review your code internally before merging it.
19
-
We work to ensure all contributors receive appropriate recognition for their contributions, at least by acknowledging them in our release notes.
24
+
## Security Scans
25
+
To ensure that all submissions meet our security and quality standards, we perform security
26
+
scans using internal SAS infrastructure. Reporting of any Common Vulnerabilities and Exposures
27
+
(CVEs) that are detected is not available in this project at this time.
-[AWS CLI](https://aws.amazon.com/cli) (optional; useful as an alternative to the AWS Web Console) v2.17.58
53
+
-[AWS CLI](https://aws.amazon.com/cli) (optional; useful as an alternative to the AWS Web Console) v2.24.16
54
54
55
55
#### Docker Requirements:
56
56
57
57
-[Docker](https://docs.docker.com/get-docker/)
58
58
59
59
## Getting Started
60
60
61
-
Ubuntu 18.04 LTS is the operating system that is used on the jump server and NFS server VMs. Ubuntu creates the `/mnt` location as an ephemeral drive, so it cannot be used as the root location of the `jump_rwx_filestore_path` variable.
61
+
Ubuntu 20.04 LTS is the operating system that is used on the jump server and NFS server VMs. Ubuntu creates the `/mnt` location as an ephemeral drive, so it cannot be used as the root location of the `jump_rwx_filestore_path` variable.
| cluster_iam_role_arn | ARN of the pre-existing IAM role for the EKS cluster | string | null | If an existing EKS cluster IAM role is being used, the IAM role's 'ARN' is required. |
190
+
| cluster_iam_role_arn |Amazon Resource Name (ARN) of the pre-existing IAM role for the EKS cluster | string | null | If an existing EKS cluster IAM role is being used, the IAM role's 'ARN' is required. |
191
191
| workers_iam_role_arn | ARN of the pre-existing IAM role for the cluster node VMs | string | null | If an existing EKS node IAM role is being used, the IAM role's 'ARN' is required. |
192
192
193
193
The cluster IAM role must include three AWS-managed policies and one custom policy.
| ssh_public_key | File name of public ssh key for jump and nfs VM | string | "~/.ssh/id_rsa.pub" | Required with `create_jump_vm=true` or `storage_type=standard`|
268
268
| cluster_api_mode | Public or private IP for the cluster api| string|"public"|Valid Values: "public", "private" |
269
+
| authentication_mode | The authentication mode for the EKS cluster.| string|"API_AND_CONFIG_MAP"| Valid values are CONFIG_MAP, API or API_AND_CONFIG_MAP |
270
+
| admin_access_entry_role_arns | Create an EKS access entry associated with the AmazonEKSClusterAdminPolicy for each of the existing IAM role ARNs that are included in this list. | list of strings ||**Note:** Do not include the assumed-role that is used to authenticate to Terraform in this list. The format for role ARNs resembles the following example: "arn:aws:iam::<Account_ID>:role/<rolename>"|
269
271
270
272
## Node Pools
271
273
@@ -388,8 +390,8 @@ Each server element, like `foo = {}`, can contain none, some, or all of the para
| server_version | The version of the PostgreSQL server | string | "15" | Refer to the [SAS Viya platform Administration Guide](https://documentation.sas.com/?cdcId=sasadmincdc&cdcVersion=default&docsetId=itopssr&docsetTarget=p05lfgkwib3zxbn1t6nyihexp12n.htm#p1wq8ouke3c6ixn1la636df9oa1u) for the supported versions of PostgreSQL for the SAS Viya platform. |
391
-
| instance_type | The VM type for the PostgreSQL Server | string | "db.m5.xlarge" ||
392
-
| storage_size | Max storage allowed for the PostgreSQL server in MB| number |50||
393
+
| instance_type | The VM type for the PostgreSQL Server | string | "db.m6idn.xlarge" ||
394
+
| storage_size | Max storage allowed for the PostgreSQL server in GB| number |128||
393
395
| backup_retention_days | Backup retention days for the PostgreSQL server | number | 7 | Supported values are between 7 and 35 days. |
394
396
| storage_encrypted | Encrypt PostgreSQL data at rest | bool | false||
395
397
| administrator_login | The Administrator Login for the PostgreSQL Server | string | "pgadmin" | The admin login name can not be 'admin', must start with a letter, and must be between 1-16 characters in length, and can only contain underscores, letters, and numbers. Changing this forces a new resource to be created |
0 commit comments