multiple bundle

[jjhwan-h]

Hello, I’ve fallen in love with OPA

When using a single bundle, everything works fine. However, when I try to use two bundles, OPA fails to run.

Does the OPA Go SDK support managing multiple bundles?

config := []byte(fmt.Sprintf(`{
		"services": {
			"test": {
				"url": %q
			}
		},
		"bundles": {
			"category1": {
				"service":"test",
				"resource": "bundles/category1.tar.gz",
				"persist": true,
				"polling":{
					"min_delay_seconds": 30,
					"max_delay_seconds": 50
				}
			},
			"category2": {
				"service":"test",
				"resource": "bundles/category2.tar.gz",
				"persist": true,
				"polling":{
					"min_delay_seconds": 30,
					"max_delay_seconds": 50
				}
			}
		},
		"decision_logs": {
			"console": false
		}
	}`, viper.GetString("BUNDLESERVER")))

category1's manifest

{
  "revision" : "category1",
  "roots": ["abc/category1","def/category1"]
}

category2's manifest

{
  "revision" : "category2",
  "roots": ["abc/category2","def/category2"]
}

[anderseknert]

Hi there, and wow, that makes two of us then ❤️

As for your issue, the SDK should work the same way as a config file provided to a standalone server (opa run --server --config-file ..). When you say OPA fails to run, how does that manifest? Do you see anything in the logs? Testing the same configuration with opa run may be an option worth trying, if only to see if you can get more information about the error.

[jjhwan-h]

I have set up a custom bundle server and I want to download multiple bundles from it using the OPA Go SDK.

The bundles on the bundle server are created by using the opa build command. Before creating each bundle, the directory structure and manifest files look like this:

category1 bundle

tree -a .
.
├── .manifest
├── abc
│   └── category1.rego
└── def
    └── data.json

2 directories, 3 files

.manifest:

{
  "revision": "category1",
  "roots": ["category1/abc", "category1/def"]
}

category2 bundle

.
├── .manifest
├── abc
│   └── category2.rego
└── def
    └── data.json

2 directories, 3 files

.manifest:

{
  "revision": "category2",
  "roots": ["category2/abc", "category2/def"]
}

Now, I am writing the following configuration for the OPA Go SDK:

// default bundle
config := []byte(fmt.Sprintf(`{
		"services": {
			"test": {
				"url": %q
			}
		},
		"bundles": {
			"category1": {
				"service": "test",
				"resource": "bundles/category1.tar.gz",
				"persist": true,
				"polling": {
					"min_delay_seconds": 30,
					"max_delay_seconds": 50
				}
			},
			"category2": {
				"service": "test",
				"resource": "bundles/category2.tar.gz",
				"persist": true,
				"polling": {
					"min_delay_seconds": 30,
					"max_delay_seconds": 50
				}
			}
		},
		"decision_logs": {
			"console": true
		}
	}`, viper.GetString("BUNDLESERVER")))

When I call sdk.New, if I use only one bundle, either "category1" or "category2", it works fine. But when I add both bundles as shown above, only one of the bundles gets created in .opa/bundles/, and the context times out.

opa, err := sdk.New(ctx, sdk.Options{
		ID:     "opa-test-1",
		Config: bytes.NewReader(config),
	})

Other posts suggest that multiple bundles are supported, so I suspect the issue might be with the manifest file configuration.

Is the problem with the manifest file?

[jjhwan-h]

When running opa run -s -b ./bundles/category1.tar.gz -b ./bundles/category2.tar.gz, I get the following error:

error: initialization error: detected overlapping roots in bundle manifest with: [./bundles/category1.tar.gz ./bundles/category2.tar.gz]

It seems like the roots in the manifest are not overlapping, so what could be the problem?