Skip to content

Commit bc3bfc4

Browse files
committed
Fix issue with ssm variables not found
The variable resolution for ss has the possibility when a parameter is not foudn to use a fallback value, that is based on the error code. The V3 error code is not the same then the v2 one, for the ease I just check also for the v3 code, as it is the only place in the core code to check for the that kind of code
1 parent 4c48292 commit bc3bfc4

File tree

1 file changed

+1
-1
lines changed
  • lib/configuration/variables/sources/instance-dependent

1 file changed

+1
-1
lines changed

lib/configuration/variables/sources/instance-dependent/get-ssm.js

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ module.exports = (serverlessInstance) => {
3737
);
3838
} catch (error) {
3939
// Check for normalized error code instead of native one
40-
if (error.code === 'AWS_S_S_M_GET_PARAMETER_PARAMETER_NOT_FOUND') return null;
40+
if (error.code === 'AWS_S_S_M_GET_PARAMETER_PARAMETER_NOT_FOUND' || error.code === 'ParameterNotFound') return null;
4141
throw error;
4242
}
4343
})();

0 commit comments

Comments
 (0)